The Runtime Complexity (innermost) of the given CpxTRS could be proven to be BOUNDS(1, n^1).

0 CpxTRS
↳1 DependencyGraphProof (BOTH BOUNDS(ID, ID), 14 ms)
↳2 CpxTRS
↳3 CpxTrsToCdtProof (BOTH BOUNDS(ID, ID), 0 ms)
↳4 CdtProblem
↳5 CdtLeafRemovalProof (BOTH BOUNDS(ID, ID), 0 ms)
↳6 CdtProblem
↳7 CdtRhsSimplificationProcessorProof (BOTH BOUNDS(ID, ID), 0 ms)
↳8 CdtProblem
↳9 CdtUsableRulesProof (⇔, 0 ms)
↳10 CdtProblem
↳11 CdtRuleRemovalProof (UPPER BOUND(ADD(n^1)), 53 ms)
↳12 CdtProblem
↳13 SIsEmptyProof (BOTH BOUNDS(ID, ID), 0 ms)
↳14 BOUNDS(1, 1)

(0) Obligation:

The Runtime Complexity (innermost) of the given CpxTRS could be proven to be BOUNDS(1, n^1).


The TRS R consists of the following rules:

from(X) → cons(X, n__from(n__s(X)))
after(0, XS) → XS
after(s(N), cons(X, XS)) → after(N, activate(XS))
from(X) → n__from(X)
s(X) → n__s(X)
activate(n__from(X)) → from(activate(X))
activate(n__s(X)) → s(activate(X))
activate(X) → X

Rewrite Strategy: INNERMOST

(1) DependencyGraphProof (BOTH BOUNDS(ID, ID) transformation)

The following rules are not reachable from basic terms in the dependency graph and can be removed:
after(s(N), cons(X, XS)) → after(N, activate(XS))

(2) Obligation:

The Runtime Complexity (innermost) of the given CpxTRS could be proven to be BOUNDS(1, n^1).


The TRS R consists of the following rules:

activate(n__from(X)) → from(activate(X))
from(X) → cons(X, n__from(n__s(X)))
from(X) → n__from(X)
after(0, XS) → XS
s(X) → n__s(X)
activate(X) → X
activate(n__s(X)) → s(activate(X))

Rewrite Strategy: INNERMOST

(3) CpxTrsToCdtProof (BOTH BOUNDS(ID, ID) transformation)

Converted Cpx (relative) TRS to CDT

(4) Obligation:

Complexity Dependency Tuples Problem
Rules:

activate(n__from(z0)) → from(activate(z0))
activate(z0) → z0
activate(n__s(z0)) → s(activate(z0))
from(z0) → cons(z0, n__from(n__s(z0)))
from(z0) → n__from(z0)
after(0, z0) → z0
s(z0) → n__s(z0)
Tuples:

ACTIVATE(n__from(z0)) → c(FROM(activate(z0)), ACTIVATE(z0))
ACTIVATE(z0) → c1
ACTIVATE(n__s(z0)) → c2(S(activate(z0)), ACTIVATE(z0))
FROM(z0) → c3
FROM(z0) → c4
AFTER(0, z0) → c5
S(z0) → c6
S tuples:

ACTIVATE(n__from(z0)) → c(FROM(activate(z0)), ACTIVATE(z0))
ACTIVATE(z0) → c1
ACTIVATE(n__s(z0)) → c2(S(activate(z0)), ACTIVATE(z0))
FROM(z0) → c3
FROM(z0) → c4
AFTER(0, z0) → c5
S(z0) → c6
K tuples:none
Defined Rule Symbols:

activate, from, after, s

Defined Pair Symbols:

ACTIVATE, FROM, AFTER, S

Compound Symbols:

c, c1, c2, c3, c4, c5, c6

(5) CdtLeafRemovalProof (BOTH BOUNDS(ID, ID) transformation)

Removed 5 trailing nodes:

FROM(z0) → c4
FROM(z0) → c3
S(z0) → c6
ACTIVATE(z0) → c1
AFTER(0, z0) → c5

(6) Obligation:

Complexity Dependency Tuples Problem
Rules:

activate(n__from(z0)) → from(activate(z0))
activate(z0) → z0
activate(n__s(z0)) → s(activate(z0))
from(z0) → cons(z0, n__from(n__s(z0)))
from(z0) → n__from(z0)
after(0, z0) → z0
s(z0) → n__s(z0)
Tuples:

ACTIVATE(n__from(z0)) → c(FROM(activate(z0)), ACTIVATE(z0))
ACTIVATE(n__s(z0)) → c2(S(activate(z0)), ACTIVATE(z0))
S tuples:

ACTIVATE(n__from(z0)) → c(FROM(activate(z0)), ACTIVATE(z0))
ACTIVATE(n__s(z0)) → c2(S(activate(z0)), ACTIVATE(z0))
K tuples:none
Defined Rule Symbols:

activate, from, after, s

Defined Pair Symbols:

ACTIVATE

Compound Symbols:

c, c2

(7) CdtRhsSimplificationProcessorProof (BOTH BOUNDS(ID, ID) transformation)

Removed 2 trailing tuple parts

(8) Obligation:

Complexity Dependency Tuples Problem
Rules:

activate(n__from(z0)) → from(activate(z0))
activate(z0) → z0
activate(n__s(z0)) → s(activate(z0))
from(z0) → cons(z0, n__from(n__s(z0)))
from(z0) → n__from(z0)
after(0, z0) → z0
s(z0) → n__s(z0)
Tuples:

ACTIVATE(n__from(z0)) → c(ACTIVATE(z0))
ACTIVATE(n__s(z0)) → c2(ACTIVATE(z0))
S tuples:

ACTIVATE(n__from(z0)) → c(ACTIVATE(z0))
ACTIVATE(n__s(z0)) → c2(ACTIVATE(z0))
K tuples:none
Defined Rule Symbols:

activate, from, after, s

Defined Pair Symbols:

ACTIVATE

Compound Symbols:

c, c2

(9) CdtUsableRulesProof (EQUIVALENT transformation)

The following rules are not usable and were removed:

activate(n__from(z0)) → from(activate(z0))
activate(z0) → z0
activate(n__s(z0)) → s(activate(z0))
from(z0) → cons(z0, n__from(n__s(z0)))
from(z0) → n__from(z0)
after(0, z0) → z0
s(z0) → n__s(z0)

(10) Obligation:

Complexity Dependency Tuples Problem
Rules:none
Tuples:

ACTIVATE(n__from(z0)) → c(ACTIVATE(z0))
ACTIVATE(n__s(z0)) → c2(ACTIVATE(z0))
S tuples:

ACTIVATE(n__from(z0)) → c(ACTIVATE(z0))
ACTIVATE(n__s(z0)) → c2(ACTIVATE(z0))
K tuples:none
Defined Rule Symbols:none

Defined Pair Symbols:

ACTIVATE

Compound Symbols:

c, c2

(11) CdtRuleRemovalProof (UPPER BOUND(ADD(n^1)) transformation)

Found a reduction pair which oriented the following tuples strictly. Hence they can be removed from S.

ACTIVATE(n__from(z0)) → c(ACTIVATE(z0))
ACTIVATE(n__s(z0)) → c2(ACTIVATE(z0))
We considered the (Usable) Rules:none
And the Tuples:

ACTIVATE(n__from(z0)) → c(ACTIVATE(z0))
ACTIVATE(n__s(z0)) → c2(ACTIVATE(z0))
The order we found is given by the following interpretation:
Polynomial interpretation :

POL(ACTIVATE(x1)) = [2]x1   
POL(c(x1)) = x1   
POL(c2(x1)) = x1   
POL(n__from(x1)) = [1] + x1   
POL(n__s(x1)) = [1] + x1   

(12) Obligation:

Complexity Dependency Tuples Problem
Rules:none
Tuples:

ACTIVATE(n__from(z0)) → c(ACTIVATE(z0))
ACTIVATE(n__s(z0)) → c2(ACTIVATE(z0))
S tuples:none
K tuples:

ACTIVATE(n__from(z0)) → c(ACTIVATE(z0))
ACTIVATE(n__s(z0)) → c2(ACTIVATE(z0))
Defined Rule Symbols:none

Defined Pair Symbols:

ACTIVATE

Compound Symbols:

c, c2

(13) SIsEmptyProof (BOTH BOUNDS(ID, ID) transformation)

The set S is empty

(14) BOUNDS(1, 1)